Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Don't repeatedly mark queued tasks as ready to run. #1789

Merged
merged 4 commits into from
Apr 20, 2016

Conversation

hjoliver
Copy link
Member

Close #1787

New logic explained by the new in-source comment.

Test battery passes here.

@matthewrmshin - please review/assign

(I can probably make a new test for this, that relies on counting logged iterations through the main scheduling loop in a suite with two tasks - one queued task and one running ... but that'll have to be tomorrow).

@hjoliver hjoliver added this to the next-release milestone Apr 12, 2016
@matthewrmshin matthewrmshin added the bug Something is wrong :( label Apr 12, 2016
@matthewrmshin
Copy link
Contributor

I guess this was missed by #1745.

Looks OK. Test battery passes. I cannot think of a good way to add an automated test for this, however.

@benfitzpatrick please review 2.

local FILE=$2
local COUNT=$3
local TEST_NAME=$(basename "$FILE")-count-ok
NEW_COUNT=$(grep -e "$BRE" "$FILE" | wc -l)
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Could use grep -c to count it?

@benfitzpatrick
Copy link
Contributor

One comment, otherwise good to go.

@hjoliver
Copy link
Member Author

I've made the one small suggested change and verified it's correctness. I'll take "otherwise good to go" as license to merge now.

@hjoliver hjoliver merged commit 52fc524 into cylc:master Apr 20, 2016
@hjoliver hjoliver deleted the 1787.fix-queued-task-processing branch April 20, 2016 23:52
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something is wrong :(
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants